Methods and apparatus to measure exposure to streaming media

ABSTRACT

Methods and apparatus to measure exposure to streaming media are disclosed. An example apparatus includes an event listener to listen for an event notification based on a playback position of a first media segment of a multi-segment media. The example apparatus includes a metadata handler to update a multi-file counter with an offset based on a duration of the first media segment, detect that a second media segment is a segment of the multi-segment media, determine a playback time within the second media segment, add the playback time to the multi-file counter to determine a corresponding playback time of the multi-segment media, and attempt to perform a lookup of a metadata tag in a table based on the playback time of the multi-segment media. The example apparatus includes and a transmitter to transmit the metadata tag corresponding to the playback time of the multi-segment media to an audience measurement entity.

RELATED APPLICATIONS

This patent arises from a continuation of U.S. patent application Ser. No. 16/416,986, filed on May 20, 2019, and entitled “METHODS AND APPARATUS TO MEASURE EXPOSURE TO STREAMING MEDIA,” which is a continuation of U.S. patent application Ser. No. 15/701,397, filed on Sep. 11, 2017, and entitled “METHODS AND APPARATUS TO MEASURE EXPOSURE TO STREAMING MEDIA,” which is a continuation of U.S. patent application Ser. No. 14/725,877, filed on May 29, 2015, and entitled “METHODS AND APPARATUS TO MEASURE EXPOSURE TO STREAMING MEDIA.” Priority to U.S. patent application Ser. Nos. 15/701,397, 14/725,877, and 16/416,986 is claimed. U.S. patent application Ser. Nos. 15/701,397, 14/725,877, and 16/416,986 are hereby incorporated herein by reference in their entireties.

FIELD OF THE DISCLOSURE

This disclosure relates generally to measuring media exposure, and, more particularly, to methods and apparatus to measure exposure to streaming media.

BACKGROUND

Streaming enables media to be delivered to and presented by a wide variety of media presentation devices, such as desktop computers, laptop computers, tablet computers, personal digital assistants, smartphones, set top boxes, game consoles, etc. A significant portion of media (e.g., content and/or advertisements) is presented via streaming to such devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example system for measuring exposure to streaming media.

FIG. 2 is a block diagram of an example implementation of the media monitor of FIG. 1.

FIG. 3 illustrates example Hypertext Markup Language (HTML) instructions representing a webpage that may be displayed by the media monitor of FIG. 2 when included in the client device of FIG. 1.

FIG. 4 illustrates example metadata included in a media file presented that may be monitored by the media monitor of FIG. 1.

FIG. 5 illustrates an example of monitoring a media presentation including dynamically inserted media.

FIG. 6 is a flowchart representative of example machine-readable instructions which may be executed to implement the example service provider of FIG. 1.

FIGS. 7A and 7B show a flowchart representative of example machine-readable instructions which may be executed to implement the example media monitor of FIGS. 1 and/or 2.

FIG. 8 is a block diagram of an example processor platform capable of executing the instructions of FIG. 6 to implement the service provider 120 of FIG. 1.

FIG. 9 is a block diagram of an example processor platform capable of executing the instructions of FIGS. 7A and 7B to implement the example media monitor of FIGS. 1 and/or 2.

The figures are not to scale. Wherever appropriate, the same reference numbers will be used throughout the drawing(s) and accompanying written description to refer to the same or like parts.

DETAILED DESCRIPTION

Examples disclosed herein monitor media presentations occurring at client devices. Conventional media monitoring systems either are not capable of monitoring a playback position within primary media when secondary media is inserted mid-stream, or require specialized monitoring software to be installed at a monitored device that limit the number of monitored devices that can be monitored and/or impact performance of such monitored devices. For instance, conventional media monitoring systems that do not have monitoring software installed may monitor a first portion of primary media, such as an episode of a television show being viewed in a browser application. However, when the conventional monitoring system encounters secondary media, such as an inserted advertisement used by the publisher to monetize the primary media, when the primary media resumes playback the conventional monitoring system loses track of a playback position within the entirety of the primary media and may incorrectly reset the playback position by using a playback position within a current media file. As a result, the playback position for parts of the media being presented after the inserted secondary media are incorrectly represented or not represented at all, despite those parts of the media actually being presented on the monitored device.

As used herein, the playback position refers to a time instant within the media with respect to the beginning of linear, non-time scaled playback of the media. For example, the 10 second playback position is located by playing the media from the beginning for 10 seconds at a 1:1 playback speed (i.e., 1 second of intended media duration takes 1 second to play using a media presentation device). Playback positions may be repeatedly played if, for example, a first position (e.g., 10 seconds) is traversed during playback of the media, and the playback position is adjusted to a second position (e.g., 5 seconds) prior to the first position (e.g., 10 seconds), and playback is restarted for enough time (e.g., 5 seconds or more) to traverse the first position (e.g., 10 seconds) again.

Examples disclosed herein provide media monitoring for a larger set of devices than in conventional monitoring, including devices with which a monitoring entity does not have a prior agreement or relationship, while enabling the media monitoring to determine a playback position within primary media despite the insertion of secondary media. Examples disclosed herein accurately track a playback position within primary media, even when the primary media is interrupted by secondary media and/or when the primary media is broken up into multiple files.

Examples disclosed herein collect demographic information associated with users of client devices based on identifiers (e.g., an Internet protocol (IP) address, a cookie, a device identifier, etc.) associated with those client devices. Media exposure information may then be generated based on media metadata and user demographics to indicate exposure metrics and/or demographic reach metrics for at least one of a genre, an artist, an album name, a transmitting station/server site, etc.

Some disclosed examples may be used to link demographics to the monitoring information. To link demographics to monitoring information, the audience measurement entity establishes a panel of users who have agreed to provide their demographic information and to have their streaming media activities monitored. When an individual joins the panel, they provide detailed information concerning their identity and demographics (e.g., gender, race, income, home location, occupation, etc.) to the audience measurement entity. The audience measurement entity sets a cookie (e.g., a panelist cookie) on the presentation device that enables the audience measurement entity to identify the panelist whenever the panelist accesses streamed media.

Example methods, apparatus, systems, and articles of manufacture disclosed herein may also be used to generate reports indicative of media exposure metrics on one or more different types of client devices (e.g., personal computers, portable devices, mobile phones, tablets, etc.). For example, an audience measurement entity may generate media exposure metrics based on metadata extracted from the streaming media at the client device and/or similar devices. A report is then generated based on the media exposure to indicate exposure measurements for a type of media (e.g., a genre) using different types of client devices. Thus, for example, reports indicating the popularity of watching, for instance, sports events on certain client devices (e.g., mobile devices, tablets, etc.) can be compared to other popularities of watching sports events on other client devices (e.g., televisions, personal computers, etc.).

Additionally or alternatively, popularities of different types of media across different device types may be compared. Such different types of media may be, for example, news, movies, television programming, on-demand media, Internet-based media, games, streaming games, etc. Such comparisons may be made across any type(s) and/or numbers of devices including, for example, cell phones, smart phones, dedicated portable multimedia playback devices, iPod® devices, tablet computing devices, iPad® devices, standard-definition (SD) televisions, high-definition (HD) televisions, three-dimensional (3D) televisions, stationary computers, portable computers, Internet radios, etc. Any other type(s) and/or number of media and/or devices may be analyzed. The report may also associate the media exposure metrics with demographic segments (e.g., age groups, genders, etc.) corresponding to the user(s) of the client device(s). Additionally or alternatively, the report may associate the media exposure metrics with metric indicators of popularity of artist, genre, song, title, etc., across one or more user characteristics selected from one or more demographic segment(s), one or more age group(s), one or more gender(s), and/or any other user characteristic(s).

In some examples, the media exposure metrics are used to determine demographic reach of streaming media, ratings for streaming media, engagement indices for streaming media, user affinities associated with streaming media, and/or any other audience measure metric associated with streaming media and/or locally stored media. In some examples, the media exposure metrics are audience share metrics indicative of percentages of audiences for different device types that accessed the same media. For example, a first percentage of an audience may be exposed to news media via smart phones, while a second percentage of the audience may be exposed to the same news media via tablets.

Disclosed example methods include extracting a metadata tag from a first media part, where the metadata tag corresponds to a playback position in a second media part and the first and second media parts are portions of a first item of media. The disclosed example methods further include detecting a third media part that is not part of the first item of media when playback of the first media part is completed and, in response to completion of playback of the first media part or detecting the third media part, storing a first duration of the first media part as an offset value. The disclosed example methods further include detecting the second media part when playback of the third media part is completed and, while the second media part is being played, looking up the metadata tag when the playback position is traversed, traversal of the playback position being identified based on the offset value. The disclosed example methods further include sending the metadata tag to an audience measurement entity based on the looking up of the metadata tag.

Some disclosed example methods further include detecting a fourth media part that is not part of the first item of media when playback of the second media part is completed and, in response to completion of playback of the second media part or detecting the fourth media part, setting the offset value based on the first duration and a second duration of the second media part. These disclosed example methods further include, when playback of the fourth media part is completed, detecting a fifth media part that is a portion of the first item of media, where a second metadata tag corresponds to a second playback position within a third duration of the fifth media par. These disclosed example methods further include looking up the second metadata tag when the second playback position is traversed while the fifth media part is being played, where traversal of the second playback position is identified based on the offset value.

Some disclosed example methods further include storing the metadata tag in a data structure using playback position as a lookup key. In some disclosed examples, the detecting of the third media part includes detecting a media insertion marker. In some such examples, the metadata tag is associated with the audience measurement entity, and the detecting of the third media part further includes determining that the third media part does not have metadata tags associated with the audience measurement entity.

In some disclosed example methods, the sending of the metadata tag to the audience measurement entity is in response to traversal of the playback position. Some disclosed example methods further include sending a request for the first media part to a server via a communications network, and receiving instructions to perform the extracting of the metadata tag, where the detecting of the third media part, the storing of the first duration, the detecting of the second media part, and the looking up of the metadata tag are in a response to the request.

Some disclosed example methods further include looking up a second metadata tag that corresponds to a second playback position in the first media part when the second playback position is traversed while the first media part is being played, where the second playback position is based on the portion of the first media part being played.

Disclosed example apparatus include a media presenter, a metadata retriever, a file detector, a duration setter, and a transmitter. In the disclosed example apparatus, the media presenter presents media. In the disclosed example apparatus, a metadata retriever is to: extract a metadata tag from a first media part, where the metadata tag corresponds to a playback position in a second media part, and the first and second media parts are portions of a first item of media. In the disclosed example apparatus, the metadata retriever also looks up the metadata tag when the playback position is traversed while the second media part is being played, where traversal of the playback position is identified based on an offset value. In the disclosed example apparatus, the file detector is to detect a third media part that is not part of the first item of media when playback of the first media part is completed, and detect the second media part when playback of the third media part is completed. In the disclosed example apparatus the duration setter stores a first duration of the first media part as the offset value in response to completion of playback of the first media part or detecting the third media part. In the disclosed example apparatus, the transmitter sends the metadata tag to an audience measurement entity based on the looking up of the metadata tag.

Some disclosed example apparatus further include a structure generator that stores the extracted metadata tag in a data structure using the playback position as a lookup key, where the metadata retriever look ups the metadata tag in the data structure. In some examples, the file detector determines whether the second media part is part of the first item of media and determines whether third media part is part of the first item of media.

Some disclosed example apparatus further include a metadata converter to convert a uniform resource locator in the metadata tag into a request for the uniform resource locator. In some examples, the metadata retriever is to looks up a second metadata tag that corresponds to a second playback position in the first media part when the second playback position is traversed while the first media part is being played, where the second playback position is based on the portion of the first media part being played.

In some disclosed examples, the file detector detects the third media part by detecting a media insertion marker. In some examples, the metadata tag is associated with the audience measurement entity, and the file detector detects the third media part by determining that the third media part does not have metadata tags associated with the audience measurement entity.

FIG. 1 is a diagram of an example system 100 constructed in accordance with the teachings of this disclosure for measuring exposure to streaming media. The example system 100 of FIG. 1 monitors media provided by an example media provider 110 for presentation on client devices. The example system 100 includes an example service provider 120, an example network 150, an example client device 160, an example media monitor 165, and an example central facility 170 of an audience measurement entity. While the illustrated example of FIG. 1 discloses an example implementation of the service provider 120, other example implementations of the service provider 120 may additionally or alternatively be used, such as the example implementations disclosed in co-pending U.S. patent application Ser. No. 13/341,646, which is hereby incorporated by reference herein in its entirety.

The media provider 110 of the illustrated example of FIG. 1 corresponds to any one or more media provider(s) capable of providing media for presentation at the client device 160. The media provided by the media provider(s) 110 can be any type of media, such as audio, video, multimedia, software, etc. Additionally, the media can correspond to live (e.g., broadcast) media, stored media (e.g., on-demand content), etc.

The service provider 120 of the illustrated example of FIG. 1 provides media services to the client device 160 via, for example, web pages including links (e.g., hyperlinks, embedded media, etc.) to media provided by the media provider 110. In the illustrated example, the service provider 120 modifies the media provided by the media provider 110 prior to transmitting the media to the client device 160. The example service provider 120 obtains media, prepares the media for monitoring at the client device 160, and provides the client device 160 with requested media (which has been prepared for monitoring) with the media monitor 165. In the illustrated example, the service provider 120 includes an example media identifier 125, an example transcoder 130, an example metadata embedder 135, an example marker embedder 136, an example monitor embedder 138, and an example media transmitter 140. In some examples, the service provider 120 and the media provider 110 are implemented in the same entity and/or device.

The media identifier 125 of the illustrated example of FIG. 1 is implemented by a logic circuit such as a processor executing instructions, but it could additionally or alternatively be implemented by an application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), an analog circuit, and/or other circuitry. The media identifier 125 of FIG. 1 extracts metering data (e.g., signatures, watermarks, etc.) from the media obtained from the media provider 110. For example, the media identifier 125 can implement functionality provided by a software development kit (SDK) to extract one or more audio watermarks, one or more video (e.g., image) watermarks, etc., embedded in the audio and/or video of the media obtained from the media provider 110. (For example, the media may include pulse code modulation (PCM) audio data or other types of audio data, uncompressed video/image data, etc.)

The example media identifier 125 of FIG. 1 determines (e.g., derives, decodes, converts, etc.) the metering data (e.g., such as media identifying information, source identifying information, etc.) included in or identified by a watermark embedded in the media and converts this metering data and/or the watermark itself into a text and/or binary format for inclusion in an ID3 tag and/or other data type (e.g., text, binary, etc.) for transmission as metadata (e.g., such as with a playlist or electronic program guide) accompanying the streaming media. For example, the code/watermark itself may be extracted and inserted as metadata in, for example, a text or binary format in the ID3 tag. Thus, the metadata and/or media-identifying metadata included in the ID3 tag may be a text or binary representation of a code, a watermark, and/or metadata or data identified by a code and/or watermark, a destination URL that is to be requested by the monitor (e.g., as a dummy request), etc. For example, the ID3 tag may include a URL corresponding to the central facility 170 that the media monitor 165 is to request from the central facility 170 upon receiving the ID3 tag.

The example transcoder 130 of the illustrated example of FIG. 1 is implemented by a logic circuit such as a processor executing instructions, but could additionally or alternatively be implemented by an analog circuit, application-specific integrated circuit (ASIC), a digital signal processor (DSP), a field-programmable gate array (FPGA), and/or other circuitry. In some examples, the transcoder 130 and the media identifier 125 are implemented by the same physical processor. In the illustrated example, the transcoder 130 employs any appropriate technique(s) to transcode and/or otherwise process the received media into a form suitable for streaming (e.g., a streaming format). For example, the transcoder 130 of the illustrated example transcodes the media in accordance with Moving Picture Experts Group (MPEG) 4 audio/video compression for use via the Hypertext Transfer Protocol (HTTP) Live Streaming (HLS) protocol.

In some examples, the transcoder 130 outputs transcoded media into multiple media files that collectively make up the entirety of the received media. The media files for a media item may be transmitted individually in response to requests for respective ones of the media files. For example, a first media file that includes the beginning of the media item is first transmitted to the client device 160, followed by a second media file that includes a second part of the media item that directly follows the part included in the first media file. The media files may have standard, calculated, and/or arbitrary lengths that may be made as equal as practicable or may be different.

The metadata embedder 135 of the illustrated example of FIG. 1 is implemented by a logic circuit such as a processor executing instructions, but could additionally and/or alternatively be implemented by an analog circuit, ASIC, DSP, FPGA, and/or other circuitry. In some examples, the transcoder 130, the media identifier 125, and the metadata embedder 135 are implemented by the same physical processor.

In the illustrated example, the metadata embedder 135 embeds the metadata determined by the media identifier 125 into one or more of the media files (e.g., into respective headers of one or more of the media file(s) designated for metadata) generated by the transcoder 130. For example, the metadata embedder 135 may embed ID3 tags into an ID3 metadata portion of the media file. In some examples, the metadata embedder 135 generates the metadata based on or instead of the identification of the media by the media identifier 125.

In the illustrated example, the metadata embedder 135 embeds the metadata into an internal metadata channel, such as by encoding metadata that is in a binary and/or other appropriate data format into one or more data fields of the transport stream(s) that is(are) capable of carrying metadata. For example, the metadata embedder 135 may insert ID3 tag metadata, which corresponds to the metering metadata, into a portion of the media file designated as an ID3 portion by a specification or convention for the media file type.

In some other examples, the metadata embedder 135 embeds the metadata into the transport stream(s) that is (are) to stream the media in accordance with the HLS or other appropriate streaming protocol. Additionally or alternatively, the metadata embedder 135 may embed the metadata into an external metadata channel, such as by encoding the metadata into an M3U8 (e.g., an M3U formatted file which uses Unicode Transmission Format—8-bit) or other data file that is to be associated with (e.g., included in, appended to, sent prior to, etc.) the transport stream(s) that are to provide the streaming media to the client device 160.

In cases in which playback of the media file is to be interrupted at a selected location (e.g., to play advertisement(s) partway through playback of the media file), the example marker embedder 136 embeds markers in the media. The markers (e.g., ad markers, media insertion markers, etc.) designate the location(s) in the media at which playback is to be interrupted, such as to play advertisements. The example markers may be recognizable metadata that indicate the locations of these interruptions within the playback of the media.

In some examples, the marker embedder 136 splits up the media file into separate media files at the selected location(s) of the interruptions. For example, to insert one advertisement, the marker embedder 136 may split the media file into two media files, which are then provided to the client device 160. The marker embedder 136 may additionally generate and provide a playlist indicating that the two media files are separate but are to be played in succession, but with a third media file intervening between playback of the two media files. When the client device 160 reaches the end of the first of the media files, the example client device 160 requests a next video in the playlist from the service provider 120 or from a third-party media provider.

The example monitor embedder 138 of FIG. 1 embeds instructions to implement the media monitor 165 into a response to a request for the media, such as in a web page. For example, the monitor embedder 138 of FIG. 1 may configure HTML instructions, Javascript instructions, and/or any other code or instructions to be executed by the client device 160 (e.g., in a browser application). The example monitor embedder 138 may configure the instructions based on the media identified by the media identifier 125, a file name convention used by the transcoder 130, and/or the metadata embedded in the video by the metadata embedder 136.

The media transmitter 140 of the illustrated example of FIG. 1 is implemented by a logic circuit such as a processor executing instructions, but could additionally or alternatively be implemented by an analog circuit, ASIC, DSP, FPGA, and/or other circuitry. In some examples, the media identifier 125, the transcoder 130, the metadata embedder 135, the marker embedder 136, the monitor embedder 138, and the media transmitter 140 are implemented by the same physical processor.

The media transmitter 140 employs any appropriate technique(s) to select and/or stream the media to a requesting device, such as the client device 160. For example, the media transmitter 140 of the illustrated example selects media that has been identified by the media identifier 125, transcoded by the transcoder 130 and undergone metadata embedding by the metadata embedder 135. The media transmitter 140 then streams the media to the client device 160 via the network 150 using HLS, or any other streaming protocol(s) and/or non-streaming transfer protocol(s).

In some examples, the media identifier 125, the transcoder 130, the metadata embedder 135, and/or the marker embedder 136 prepare media for streaming regardless of whether (e.g., prior to) a request is received from the client device 160. In such examples, the already-prepared media is stored in a data store of the service provider 120 (e.g., such as in a flash memory, magnetic media, optical media, etc.). In such examples, the media transmitter 140 prepares a transport stream for streaming the already-prepared media to the client device 160 when a request is received from the client device 160. In other examples, the media identifier 125, the transcoder 130, and/or the metadata embedder 135 prepare the media for streaming in response to a request received from the client device 160.

The example network 150 of the illustrated example is the Internet. Additionally or alternatively, any other network(s) communicatively linking the service provider 120 and the client device such as, for example, a private network, a local area network (LAN), a virtual private network (VPN), etc. may be used. The network 150 may comprise any number of public and/or private networks using any type(s) of networking protocol(s).

The client device 160 of the illustrated example of FIG. 1 is a computing device that is capable of presenting streaming media provided by the media transmitter 140 via the network 150. The client device 160 may be, for example, a tablet, a desktop computer, a laptop computer, a mobile computing device, a television, a smart phone, a mobile phone, an Apple® iPad®, an Apple® iPhone®, an Apple® iPod®, an Android™ powered computing device, a Palm® webOS® computing device, etc. In the illustrated example, the client device 160 includes a media monitor 165. In some other examples, the media monitor 165 is received with an item of media to be monitored, such as instructions received in a web page that implements a media player. Example Javascript® instructions to implement the media monitor 165 are described below with reference to FIG. 3.

In the illustrated example, the media monitor 165 is implemented using a media player (e.g., a browser, a local application, etc.) that presents streaming media provided by the media transmitter 140. For example, the media monitor 165 may additionally or alternatively be implemented in Adobe® Flash® (e.g., provided in a Shockwave Flash (SWF) file), may be implemented in hypertext markup language (HTML) version 5 (HTMLS), may be implemented in Google® Chromium®, may be implemented according to the Open Source Media Framework (OSMF), may be implemented according to a device or operating system provider's media player application programming interface (API), may be implemented on a device or operating system provider's media player framework (e.g., the Apple® iOS® MPMoviePlayer software), etc., or any combination thereof. In the illustrated example, the media monitor 165 reports metering data to the central facility 170. While a single client device 160 is illustrated, any number and/or type(s) of media presentation devices may be used.

The central facility 170 of the audience measurement entity of the illustrated example of FIG. 1 includes an interface to receive reported metering information (e.g., metadata) from the media monitor 165 of the client device 160 via the network 150. In the illustrated example, the central facility 170 includes a HTTP interface to receive HTTP requests that include the metering information. Example metering information includes requests (e.g., HTTP requests) that include unique information identifying the media being presented and/or a specific portion of that media. Additionally or alternatively, any other method(s) to receive metering information may be used such as, for example, an HTTP Secure protocol (HTTPS), a file transfer protocol (FTP), a secure file transfer protocol (SFTP), etc. In the illustrated example, the central facility 170 stores and analyzes metering information received from a plurality of different client devices. For example, the central facility 170 may sort and/or group metering information by media provider 110 (e.g., by grouping all metering data associated with a particular media provider 110). Any other processing of metering information may additionally or alternatively be performed.

FIG. 2 is a block diagram of an example implementation of the media monitor 165 of FIG. 1. The media monitor 165 of the illustrated example of FIG. 2 includes an example media presenter 210, an example event listener 220, an example metadata handler 230, an example metadata converter 240, and an example transmitter 250.

The media presenter 210 of the illustrated example of FIG. 2 is implemented by a processor executing instructions, but it could additionally or alternatively be implemented by an analog circuit, an ASIC, DSP, FPGA, and/or other circuitry. In the illustrated example, the media presenter 210 is an HTMLS media player implemented in a browser or other application. In some other examples, the media presenter 210 interacts with a QuickTime® application programming interface (API) to display media via the client device 160. Any other media presenting framework may additionally or alternatively be employed. For example, the example media presenter 210 may interact with an Adobe® Flash® media presentation framework.

The example event listener 220 of the illustrated example of FIG. 2 is implemented by a logic circuit such as a processor executing instructions, but it could additionally or alternatively be implemented by an analog circuit, an ASIC, DSP, FPGA, and/or other circuitry. In some examples, the media presenter 210 and the event listener 220 are implemented by the same physical processor. In the illustrated example, the event listener 220 interfaces with JavaScript functions to enable reception of and/or listening for an event notification.

Example event notifications include the media presenter 210 reaching designated locations and/or intervals within the media playback. For example, events may be located every X seconds within the media, based on a playback position of the media (e.g., the number of seconds from the beginning of the media). The value of X represents the granularity at which the audience measurement entity wishes to monitor exposure to an item of media. A lower value of X (i.e., tags corresponding to more playback positions in the media) results in more data being transferred to the central facility 170.

While JavaScript is used to listen for event notifications in the illustrated example, any other framework, such as, for example, ActiveX, Microsoft Silverlight, etc., may be used to listen for event notifications.

The metadata handler 230 of the illustrated example of FIG. 2 is implemented by a logic circuit such as a processor executing instructions, but it could additionally or alternatively be implemented by an analog circuit, an ASIC, DSP, FPGA, and/or other circuitry. In some examples, the media presenter 210, the event listener 220, and the metadata handler 230 are implemented by the same physical processor. The example metadata handler 230 of FIG. 2 includes a structure generator 232, a file detector 234, a duration setter 236, and a metadata retriever 238.

In the illustrated example, the structure generator 232 retrieves metadata from the media presenter 210 upon loading of media. In the example of FIG. 2, the loaded media has a set of metadata “tags” in a metadata portion of a media file. The metadata tags correspond to playback positions in the media. In some examples, a first media file includes metadata tags for the first media files and for one or more subsequent media files. For example, if a media item of interest is split into multiple media files such that supplemental media can be inserted midstream (e.g., an advertisement insertion), the first media file in the sequence may include metadata tags corresponding to playback positions in the first media file and the subsequent media files.

In the example of FIG. 2, the structure generator 232 populates a table 260 or matrix with the metadata tags 270 and the playback positions 280 corresponding to the metadata tags 270. When the media presenter 210 reaches a playback position that corresponds to a metadata tag 270 in the table 260, the example metadata retriever 238 retrieves the metadata tag 270 corresponding to the playback position 280.

In examples in which the table 260 includes metadata tags 270 for subsequent media files in addition to the media file in which the metadata was identified, the file detector 234 and the duration setter 236 maintain a multi-file counter 290 that stores a playback position for subsequent media files. For example, when the media presenter 210 reaches the end of one media file in a sequence of multiple media files (not including any inserted media that is not part of the same media item), the example duration setter 236 stores a sum of the durations of the media files in the sequence that have been played.

For example, if one media file in the sequence has been played, and the media file has a duration of 90 seconds, at the end of playback of the media file, the duration setter 236 determines the total duration to be 90 seconds and stores 90 seconds in the multi-file counter 290. At the beginning of playback of a next media file (e.g., a second media file in the sequence having a duration of 45 seconds), the example file detector 234 determines whether the second media file is a continuation of the previous media file(s) such that the tags from the previous media files are to be used for the second media file. The file detector 234 and/or the media presenter 210 may determine the continuity of sequential media files based on comparing file names (e.g., based on a convention), by querying the provider of the media for the relationship between the files, or by any other means. For example, if the first media file has a file name (e.g., a URL) ending in “/movie_pt1.mp4” and the second media file has the same file name (e.g., a URL) except that the file name ends in “/movie_pt2.mp4,” the example file detector 234 may determine that the metadata tags from the first media file are to be used for monitoring the second media file because the URLs or names of the media files are merely incremented.

While the second media file is being played by the media presenter 210, metadata tags are extracted by adding the playback position within the second media file (e.g., measured from the beginning of the second media file) to a value of the multi-file counter 290 (e.g., 90 seconds). For example, the playback position of 20 seconds in the second media file playback is determined to correspond to a metadata tag for 110 seconds (e.g., 90 second counter value+20 second playback position), which also corresponds to the 110 second playback position in the media item. After finishing playback of the second media file, the duration setter 236 adds the 45 second duration of the second media file to the multi-file counter 290, and stores the total value of 135 seconds stored in the multi-file counter 290.

When the example event listener 220 of FIG. 2 detects an event (e.g., when the playback position of the media presenter 210 is equal to one of the positions 280 in the table 260), the example metadata retriever 238 retrieves the corresponding metadata tag 270 from the table 260 by looking up the playback position 280 in the table 260. While JavaScript is used to retrieve the metadata tag 270 in the illustrated example, any other framework, such as, for example, ActiveX, Microsoft Silverlight, etc., may be used to retrieve the metadata tag 270.

The metadata converter 240 of the illustrated example of FIG. 2 is implemented by a logic circuit such as a processor executing instructions, but it could additionally or alternatively be implemented by an analog circuit, an ASIC, DSP, FPGA, and/or other circuitry. In some examples, the media presenter 210, the event listener 220, the metadata handler 230, and the metadata converter 240 are implemented by the same physical processor. In the illustrated example, the metadata converter 240 converts the metadata tag 270 retrieved by the metadata retriever 238 into a format for transmission to the central facility 170. For example, the metadata converter 240 may encrypt, decrypt, compress, modify, etc., the metadata tag 270 and/or portions of the metadata tag 270 to, for example, reduce the amount of data to be transmitted to the central facility 170. In some examples, the metadata tags 270 represent respective URLs (e.g., unique URLs). In such examples, the metadata converter 240 converts the URL in the metadata tag 270 to an HTTP request for transmission to the central facility 170 of FIG. 1.

The transmitter 250 of the illustrated example of FIG. 2 is implemented by a logic circuit such as a processor executing instructions, but it could additionally or alternatively be implemented by an analog circuit, an ASIC, DSP, FPGA, and/or other circuitry. In some examples, the media presenter 210, the event listener 220, the metadata handler 230, the structure generator 232, the file detector 234, the duration setter 236, the metadata retriever 238, the metadata converter 240, and the transmitter 250 are implemented by the same physical processor. In the illustrated example, the transmitter 250 transmits a media monitoring message including the converted metadata tag 270 (e.g., an HTTP request including a URL defined in the metadata tag 270) to the central facility 170 via, for example, the Internet. In some examples, the metadata is transmitted in substantially real-time. In some other examples, the metadata is stored, cached, and/or buffered before being transmitted to the central facility 170. The metadata is transmitted to the central facility 170 in the illustrated example. In some other examples, the metadata is transmitted to a different destination such as, for example, a display element of the media monitor 165 and/or the client device 160. Additionally or alternatively, the transmitter 250 may transmit an identifier of the media monitor 165 and/or the client device 160 to enable the central facility 170 to correlate the metadata with a panelist, a group of panelists, a demographic, etc. In the illustrated example the central facility 170 is associated with an audience measurement company and is not involved with the delivery of media to the client device.

FIG. 3 illustrates example Hypertext Markup Language (HTML) instructions 300 representing a webpage that may be displayed by the media monitor 165 of FIG. 2 when included in the client device 160 of FIG. 1. The example instructions 300 of FIG. 3 may be provided in a web page that includes and/or loads media to be monitored by the media monitor 165.

The example instructions 300 include event configuration instructions 305, media presentation instructions 310, metadata structure instructions 315, and presentation monitoring instructions 320. The example presentation monitoring instructions 320 includes file detection instructions 330, file handling instructions 335, a metadata retrieval instruction 340, and a metadata conversion/transmission instruction 345.

The example configuration instructions 305 may be executed by the example file detector 234 of FIG. 2 to configure the event listener 220 to detect an end of a media file. For example, when the media presenter 210 finishes playback of a media file, an “end” event occurs that is detected by the example event listener 220, which may be provided to the file detector 234 (e.g., as an interrupt or exception).

The example media presentation instructions 310 may be executed by the example media presenter 210 of FIG. 2 to load and play media files. The example media presentation instructions 310 are executed when the web page is initially loaded at the media monitor 165.

The example metadata structure instructions 315 may be executed by the example structure generator 232 of FIG. 2 to identify the location(s) of metadata tags within the media file, select or extract the metadata that includes the metadata tags, split the metadata into individual metadata tags by identifying a divider character (e.g., a space, a breaking space, or any other selected data element), and placing the metadata tags split from the metadata into a data structure (e.g., an array, the table 260 of FIG. 2, etc.). In the example metadata structure instructions 315, the metadata tags are placed into the structure with an assumed or predetermined playback interval between the metadata tags. For example, the first metadata tag may correspond to a beginning of the media, and each subsequent metadata tag corresponds to a selected interval that follows the immediately prior metadata tag (e.g., tag 2 is X seconds of playback position after tag 1, etc.).

The example presentation monitoring instructions 320 may be executed by the example event listener 220, the example file detector 234, the example duration setter 236, and the example metadata retriever 238. The presentation monitoring instructions 320 are performed during playback of media by the media presenter 210 (e.g., repeatedly at intervals of X seconds), and include event monitoring instructions 325, file detection instructions 330, file handling instructions 335, metadata retrieval instruction 340, and metadata conversion/transmission instruction 345.

The example event monitoring instructions 325 may be executed by the example event listener 220 of FIG. 2 to monitor a playback status of the media presenter 210. For example, the event listener 220 determines a current playback position and a total playback position of the media file being played by the media presenter 210. The example event monitoring instructions 325 are executed at specified interval(s) to repeatedly determine the playback status.

The example file detection instructions 330 may be executed by the example file detector 234 to determine a current media file (e.g., URL of the media file, file name of the media file, etc.). The example file detection instructions 330 of FIG. 3 detect whether a media file is associated with primary media (e.g., is not secondary media, such as an advertisement, inserted midstream into primary media) or is not associated with primary media. For example, the file detection instructions 330 of FIG. 3 determine whether a file name of the media includes a designated string.

The example file detection instructions 330 are specified by the monitor embedder 138 of FIG. 1 based on the media being provided to the client device 160. In the illustrated example, the designated string is “examplevideo_” and the media file name convention follows a pattern in which the portion following the designated string is a number that is incremented for each subsequent media file that is part of the media item. For example, if the first media file is “examplevideo_0.m4v,” the second media file may be “examplevideo_1.m4v,” the third media file may be “examplevideo_2.m4v,” and so on for subsequent media files for the media item. In contrast, inserted media does not follow the media file name convention. Thus, the example file detection instructions 330 include instructions to determine file names that follow a media file name convention and file names that do not follow the media file name convention. However, the file detection instructions 330 may use any other method to distinguish between files containing primary media (e.g., media of interest) and secondary media.

The example file handling instructions 335 may be executed by the example duration setter 236 of FIG. 2 to handle a subsequent file based on whether the subsequent file corresponds to the primary media of interest or, instead, is secondary media such as an advertisement that is being inserted midstream. In the example of FIG. 3, when a media file that has finished playback is a media file of a primary media item (e.g., as determined by the file detection instructions 330), the example file handling instructions 335 include adding a duration of the media item to a total duration count (e.g., the duration_0 variable of FIG. 3). The total duration count enables the metadata retriever 238 to determine a playback position within the overall media item that is divided up into multiple media files (e.g., measured from the beginning of the media item). For example, if a third media file in the media item follows a first media file having a duration of 20 seconds and a second media file having a duration of 30 seconds (regardless of intervening secondary media that is not part of the same media item as the first, second, and third media files), the total duration used during playback of the third media file is 50 seconds. The total duration is used by the metadata retriever 238 to determine the appropriate metadata to be retrieved.

Additionally, when a media file is determined to be part of the media item, the example file handling instructions 335 add the total duration count to a current playback position determined by the media presenter 210.

The example metadata retrieval instruction 340 may be executed by the metadata retriever 238 of FIG. 2 to determine a playback position within the media, based on the playback position within the current media file (e.g., the “tiem” variable) being played by the media presenter 210 and the total of the duration(s) of any previous media file(s) played by the media presenter 210 that correspond to the same media item (e.g., the “duration_0” variable).

The example metadata conversion/transmission instruction 345 may be executed by the metadata retriever 238 and/or the metadata converter 240 of FIG. 2 to convert and/or transmit metadata. The example metadata conversion/transmission instruction 345 is a compound instruction that both accesses the metadata tag and outputs the accessed metadata tag. An example output may be an HTTP request that includes a request for a URL specified in the metadata tag.

FIG. 4 illustrates example metadata 400 included in a media file presented that may be monitored by the media monitor 165 of FIG. 1. The example metadata 400 includes multiple metadata tags 405-430. The example metadata 400 of FIG. 4 is shown in a string format in which it may be found in a metadata portion (e.g., a header portion) of a media file. Alternating ones of the metadata tags 405-430 are shown in boldface to illustrate where one tag ends and the subsequent tag begins.

The example structure generator 232 of FIG. 2 executes the example metadata structure instructions 315 of FIG. 3 to insert the example metadata tags 405-430 into a data structure, such as the table 260 of FIG. 2. In the example of FIG. 4, the structure generator 232 may store the metadata tag 405 as corresponding to a first time in the media (e.g., the beginning of the media), store the metadata tag 410 as corresponding to a second time in the media (e.g., 2 seconds from the beginning of the media), store the metadata tag 415 as corresponding to a third time in the media (e.g., 4 seconds from the beginning of the media), and so on for the metadata tags 420-430 at similar intervals.

Each of the example metadata tags 405-430 of FIG. 4 includes a unique URL. When one of the metadata tags 405-430 is retrieved by the metadata retriever 238 (e.g., in response to the media presenter 210 reaching the media position corresponding to the metadata tag 405-430), the example metadata converter 240 converts the retrieved metadata tag 405-430 to an HTTP request for the URL specified in the retrieved metadata tag 405-430. Upon receiving the HTTP request, the example central facility logs an exposure to the corresponding 2 second portion of the media file.

FIG. 5 illustrates an example of monitoring a media presentation including dynamically inserted media. The example of FIG. 5 may be performed by the example media monitor 165 of FIGS. 1 and/or 2. The example operation of the media monitor 165 is shown along a timeline 502, and is divided into four example time periods 504, 506, 508, 510 for ease of discussion.

The example media in the example of FIG. 5 includes three parts: media part A 512, media part B 514, and media part C 516. During the first time period 504, the example media presenter 210 loads media part A 512. When the media part A 512 is loaded, the example structure generator 232 of FIG. 2 determines that there are metadata tags in the media file and builds a table 518 (e.g., the table 260 of FIG. 2) including the metadata tags.

The example media presenter 210 begins playing the media part A 512. During playback, the event listener 220 monitors the status of the media presenter 210 (e.g., the playback position, the media source). At Current Time=2 (e.g., the playback position of the media presenter 210 is at 2 seconds), the example metadata handler 230 (e.g., via the metadata retriever 238) identifies that an event output by the event listener 220 is a playback position that corresponds to a metadata tag (e.g., Tag 1) in the table 518. The metadata retriever 238 reads Tag 1 (e.g., a first URL) from the table 518, the metadata converter 240 converts Tag 1 to an HTTP request containing the data stored in Tag 1 (e.g., the first URL), and the transmitter 250 transmits the request (e.g., to the central facility 170 of FIG. 1).

Similarly, at Current Time=4 (e.g., the playback position of the media presenter 210 is at 4 seconds), the example metadata handler 230 (e.g., via the metadata retriever 238) identifies that an event output by the event listener 220 is a playback position that corresponds to a metadata tag (e.g., Tag 2) in the table 518. The metadata retriever 238 reads Tag 2 (e.g., a second URL) from the table 518, the metadata converter 240 converts Tag 2 to an HTTP request containing the data stored in Tag 2 (e.g., the second URL), and the transmitter 250 transmits the request (e.g., to the central facility 170 of FIG. 1).

At Current Time=100, the example file detector 234 determines that an end of the media file has been reached based on the event listener 220 listening for an end of a media file being reached by the media presenter 210. In some other examples, the file detector 234 identifies that a marker has been reached by the media presenter 210 based on an output by the media presenter 210. Based on determining that the end of the media file has been reached, and that the media file is part of the media item being monitored (e.g., based on a file name convention), the example duration setter 236 stores the duration of the media part A 512 as an offset variable 522.

During the example second time period 506 of FIG. 5, an advertisement 524 is loaded and presented as a mid-stream presentation. However, any other type of media may be presented mid-stream, instead of an advertisement. The example file detector 234 determines that the subsequent file being loaded by the media presenter 210 is not related to the media part A 512 (e.g., based on having a different file name or any other method of detection). During the second time period 506, the metadata handler 230 does not extract metadata or provide metadata to the central facility 170.

At an end of the second time period 506, the example file detector 234 determines that an end of the media file has been reached based on the event listener 220 listening for an end of a media file being reached by the media presenter 210. Based on determining that the end of the media file has been reached, and that the media file is not part of the media item being monitored (e.g., based on the media file for the advertisement 524 not conforming to the file name convention), the example duration setter 236 does not add the duration of the advertisement 524 to the total stored offset.

During the example third time period 508, the example file detector 234 determines that the media being presented (e.g., media part B 514) is part of the same media item as the media part A 512 in the first time period 504 (e.g., based on the media part A 512 and the media part B 514 following a same file name convention).

The example media presenter 210 begins playing the media part B 514. During playback, the event listener 220 monitors the status of the media presenter 210 (e.g., the playback position, the media source). At Current Time=0 (e.g., the playback position of the media presenter 210 is at 0 seconds), the example metadata handler 230 (e.g., via the metadata retriever 238) identifies that an event output by the event listener 220 is a playback position that corresponds to a metadata tag (e.g., Tag (0+100)/2=Tag 50) in the table 518. The metadata retriever 238 reads Tag 50 (e.g., a URL) from the table 518, the metadata converter 240 converts Tag 50 to an HTTP request containing the data stored in Tag 50 (e.g., the URL), and the transmitter 250 transmits the request (e.g., to the central facility 170 of FIG. 1). The example metadata retriever 238 continues to add the offset of 100 to the Current Time to determine the corresponding one of the metadata tags in the table 518 during the third time period 508.

At the end of the third time period 508, the example file detector 234 determines that an end of the media part B 514 has been reached based on the event listener 220 listening for an end of a media file being reached by the media presenter 210. Based on determining that the end of the media file has been reached, and that the media file is part of the media item being monitored (e.g., based on the file name convention), the example duration setter 236 adds the duration of the media part B 514 to the offset variable 522 and stores the total as the offset variable 522. As a result, the offset variable at the beginning of the fourth time period 510 is the sum of the durations of the media part A 512 (e.g., 100 seconds) and the media part B 514 (e.g., 51 seconds).

As in the example third time period 508, during the fourth time period 510, the metadata retriever 238 adds the stored offset 522 (e.g., 151 seconds) to the playback position obtained from the media presenter 210 to determine whether the playback position corresponds to a metadata tag.

While example manners of implementing the service provider 120 and/or the media monitor 165 of FIG. 1 are illustrated in FIGS. 1 and 2, one or more of the elements, processes and/or devices illustrated in FIGS. 1 and 2 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example media identifier 125, the example transcoder 130, the example metadata embedder 135, the example marker embedder 136, the example monitor embedder 138, the example media transmitter 140, the example media presenter 210, the example event listener 220, the example metadata handler 230, the example structure generator 232, the example file detector 234, the example duration setter 236, the example metadata retriever 238, the example metadata converter 240, the example transmitter 250 and/or, more generally, the example service provider 120 and/or the example media monitor 165 of FIGS. 1 and/or 2 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example media identifier 125, the example transcoder 130, the example metadata embedder 135, the example marker embedder 136, the example monitor embedder 138, the example media transmitter 140, the example media presenter 210, the example event listener 220, the example metadata handler 230, the example structure generator 232, the example file detector 234, the example duration setter 236, the example metadata retriever 238, the example metadata converter 240, the example transmitter 250 and/or, more generally, the example service provider 120 and/or the example media monitor 165 could be implemented by one or more analog or digital circuit(s), logic circuits, programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)). When reading any of the apparatus or system claims of this patent to cover a purely software and/or firmware implementation, at least one of the example media identifier 125, the example transcoder 130, the example metadata embedder 135, the example marker embedder 136, the example monitor embedder 138, the example media transmitter 140, the example media presenter 210, the example event listener 220, the example metadata handler 230, the example structure generator 232, the example file detector 234, the example duration setter 236, the example metadata retriever 238, the example metadata converter 240, and/or the example transmitter 250 is/are hereby expressly defined to include a tangible computer readable storage device or storage disk such as a memory, a digital versatile disk (DVD), a compact disk (CD), a Blu-ray disk, etc. storing the software and/or firmware. Further still, the example the example service provider 120 and/or the example media monitor 165 of FIGS. 1 and/or 2 may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in FIGS. 1 and/or 2, and/or may include more than one of any or all of the illustrated elements, processes and devices.

A flowchart representative of example machine readable instructions for implementing the service provider 120 of FIG. 1 is shown in FIG. 6. In this example, the machine readable instructions comprise program(s) for execution by a processor such as the processor 812 shown in the example processor platform 800 discussed below in connection with FIG. 8. The program(s) may be embodied in software stored on a tangible computer readable storage medium such as a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), a Blu-ray disk, or a memory associated with the processor 812, but the entire program(s) and/or parts thereof could alternatively be executed by a device other than the processor 812 and/or embodied in firmware or dedicated hardware. Further, although the example program(s) are described with reference to the flowchart illustrated in FIG. 6, many other methods of implementing the example service provider 120 may alternatively be used. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, or combined.

A flowchart representative of example machine readable instructions for implementing the media monitor 165 of FIGS. 1 and 2 is shown in FIGS. 7A and 7B. In this example, the machine readable instructions comprise program(s) for execution by a processor such as the processor 912 shown in the example processor platform 900 discussed below in connection with FIG. 9. The program(s) may be embodied in software stored on a tangible computer readable storage medium such as a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), a Blu-ray disk, or a memory associated with the processor 912, but the entire program(s) and/or parts thereof could alternatively be executed by a device other than the processor 912 and/or embodied in firmware or dedicated hardware. Further, although the example program(s) are described with reference to the flowchart illustrated in FIG. 6, many other methods of implementing the example media monitor 165 may alternatively be used. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, or combined.

As mentioned above, the example processes of FIGS. 6 and/or 7 may be implemented using coded instructions (e.g., computer and/or machine readable instructions) stored on a tangible computer readable storage medium such as a hard disk drive, a flash memory, a read-only memory (ROM), a compact disk (CD), a digital versatile disk (DVD), a cache, a random-access memory (RAM) and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term tangible computer readable storage medium is expressly defined to include any type of computer readable storage device and/or storage disk and to exclude propagating signals and transmission media. As used herein, “tangible computer readable storage medium” and “tangible machine readable storage medium” are used interchangeably. Additionally or alternatively, the example processes of FIGS. 6 and/or 7 may be implemented using coded instructions (e.g., computer and/or machine readable instructions) stored on a non-transitory computer and/or machine readable medium such as a hard disk drive, a flash memory, a read-only memory, a compact disk, a digital versatile disk, a cache, a random-access memory and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term non-transitory computer readable medium is expressly defined to include any type of computer readable storage device and/or storage disk and to exclude propagating signals and transmission media. As used herein, when the phrase “at least” is used as the transition term in a preamble of a claim, it is open-ended in the same manner as the term “comprising” is open ended. As used in the claims of this patent, the term “a” is expressly defined to mean “one or more.”

Further, for ease of discussion, operations disclosed herein may be discussed in the context of execution by “a processor.” In keeping with the meaning of “a” as “one or more”, it is to be understood that such operations can be executed by any number (i.e., one or more) of processors. This is in keeping with the reality, well known to persons of ordinary skill in the art, that operations can be performed by one processor or by multiple processors while still meeting the end purpose of the underlying operations. For example, operations can be assigned to one processor or split among two or more processors in a same integrated circuit package (e.g., co-processors, multi-core processors, etc.) or in separate integrated circuit packages without departing from the scope or spirit of this disclosure. Moreover, processors in separate integrated circuit packages may be on a shared circuit board, on separate circuit boards, in one device, or in two or more devices. For example, in a cloud computing context separate processors remote from, and potentially unknown to, the end user may be assigned to execute operations. Therefore, unless otherwise specified, all references in this specification or the claims of this patent to “a processor” are expressly defined to include any number (i.e., one or more) of processors such that any recited operations can be assigned in any combination to the same or different processors. In short, the assignment of operations to one processor or to two or more processors is immaterial to this disclosure and the claims of this patent.

FIG. 6 is a flowchart representative of example machine-readable instructions 600 which may be executed to implement the example service provider 120 of FIG. 1 to provide media including metadata.

The example media identifier 125 receives media (e.g., from the media provider 110 of FIG. 1) (block 602). The example media identifier 125 identifies the media (block 604). The example media may include watermarks that can be extracted and decoded to identify the media.

The example transcoder 130 transcodes media into a selected format (block 606). For example, the transcoder 130 may transcode and/or otherwise process the received media for streaming or other form of transmission (e.g., a streaming or non-streaming format).

The example metadata embedder 135 generates metadata (block 608). The example metadata embedder 135 embeds the metadata into media file (block 610). For example, the metadata embedder 135 may generate unique metadata tags (e.g., ID3 tags) that are identifiable by the central facility 170. The metadata may be generated based on the identity of the media and/or in cooperation with the service provider 120. The example metadata embedder 135 embeds the metadata tags into a metadata portion of the media file.

The marker embedder 136 embeds ad markers into the media file (block 612). For example, the marker embedder 136 may embed markers into the media file that indicate where a media player is to insert advertisements mid-stream.

The example monitor embedder 138 embeds a monitor (e.g., the media monitor 165) into a web page that is used to provide the media file to the client device 160 (block 614). For example, the monitor embedder 138 may include instructions to implement the media monitor 165, such as the instructions 300 of FIG. 3. The monitor embedder 138 may customize the embedded monitor based on, for example, a file name convention of the media files so that the monitor, when executed by the client device 160, can distinguish primary media from secondary media.

The example media transmitter 140 transmits the media (e.g., including the embedded metadata) (block 616). For example, the media transmitter 140 transmits a web page including the media, the monitor, the ad markers, and the metadata. The example instructions 600 may then end.

FIGS. 7A and 7B show a flowchart representative of example machine-readable instructions 700 which may be executed to implement the example media monitor 165 of FIGS. 1 and/or 2.

The example media presenter 210 loads media (e.g., from the service provider 120 via the network 150) (block 702). For example, the media presenter 210 may load the media as part of a web page, in response to a user request for the media via an interface of the client device 160. In the example of FIGS. 7A and 7B, the web page includes the media and a monitor, and the media includes metadata tags and/or ad markers.

The example structure generator 232 identifies metadata tags in the media (block 704). The structure generator 232 adds the identified metadata tags to a data structure (block 706). For example, the structure generator 232 may add the metadata tags 270 to the table 260 of FIG. 2. The example instructions 315 of FIG. 3 may be executed by the structure generator 232 to implement blocks 704 and 706. In some examples, the metadata tags that are identified and stored correspond to media files in addition to the media file in which the metadata tags were identified.

The example media presenter 210 presents the media (block 708). For example, the media presenter 210 may initiate playback of media such as audio and/or video. During presentation of the media, the example event listener 220 determines a current time (e.g., playback position) within the presentation of the media (block 710). For example, the event listener 220 may determine a current playback position in the media relative to a beginning of a media file currently being played by the media presenter 210.

The example metadata retriever 238 determines whether the current time (e.g., the playback position), when adjusted by an offset, corresponds to a metadata tag collection time (block 712). For example, the metadata retriever 238 may determine whether the sum of the current playback position and a value stored in the multi-file counter 290 in FIG. 2 is equal to one of the playback positions 280 in the table 260.

When the current time (e.g., the playback position), when adjusted by an offset, corresponds to a metadata tag collection time (block 712), the example metadata retriever 238 determines one of the metadata tags that corresponds to the current time from the data structure (block 714). For example, the metadata retriever 238 may determine one of the metadata tags 270 in the table 260 that corresponds to a playback position. The example transmitter 250 of FIG. 2 transmits the metadata tag to an audience measurement entity (block 716). For example, the transmitter 250 may transmit the determined metadata tag to the central facility 170 of FIG. 1 via the network 150, either when the metadata tag 270 is obtained from the table 260 or when multiple metadata tags 270 have been obtained from the table for multiple playback positions (e.g., in a bulk transfer). In some examples, the metadata converter 240 converts the metadata tags to another format suitable for transmission. For example, the metadata converter 240 may convert metadata tags that contain URLs to HTTP requests for transmission by the transmitter 250.

After transmitting the determined metadata tag (block 716), or if the current time (e.g., the playback position), when adjusted by an offset, does not correspond to a metadata tag collection time (block 712), the example event listener 220 determines whether the presented media has finished (block 718). For example, the event listener 220 may identify an event, interrupt, or exception that occurs when the media presenter 210 reaches the end of the current media file. If media presentation is not finished (block 718), control returns to block 708 to continue presenting the media.

When the presented media is finished (block 718), the example metadata retriever 238 sets the offset for determining the playback position (e.g., the value of the multi-file counter 290) based on the stored offset (e.g., a current value of the multi-file counter 290) (block 720). To set the offset, the example metadata retriever 238 adds the duration of the media file that was completed to the stored offset value, and stores the sum as a new offset value.

Turning to FIG. 7B, the example file detector 234 of FIG. 2 determines whether additional media is to be played (block 722). For example, the media presenter 210 may load and play a next file in a playlist when the previous media file is completed. When another file is played, the example media presenter 210 notifies the file detector 234.

When an additional media file is to be played (block 722), the example media presenter 210 loads the next media file (block 724). The file detector 234 determines whether the loaded media item corresponds to the metadata tags in the data structure (block 726). For example, the file detector 234 may determine whether the file name of the subsequent file complies with a file naming convention for the media item. When the loaded media item corresponds to the metadata tags in the data structure (block 726), control returns to block 708 to present the media.

When the loaded media item does not correspond to the metadata tags in the data structure (e.g., the loaded media item is secondary media, such as an advertisement) (block 726), the example media presenter 210 presents the media (block 728). The event listener 220 determines whether the media being presented is finished (block 730). If the media is not finished (block 730), control returns to block 728 to continue presenting the media.

When the media is finished being presented (block 730), the example file detector 234 of FIG. 2 determines whether additional media is to be played (block 732). If an additional media file is to be played (block 732), control returns to block 724 to load the next media file.

When there are no additional media files to be played (block 732 or block 722), the example instructions 700 of FIG. 7B end. The example instructions 700 may be executed again for a subsequent media request by the client device 160.

FIG. 8 is a block diagram of an example processor platform 800 capable of executing the instructions of FIG. 6 to implement the service provider 120, the example media identifier 125, the example transcoder 130, the example metadata embedder 135, the example marker embedder 136, the example monitor embedder 138, and/or the example media transmitter 140 of FIG. 1. The processor platform 800 can be, for example, a server, a personal computer, or any other type of computing device.

The processor platform 800 of the illustrated example includes a processor 812. The processor 812 of the illustrated example is hardware. For example, the processor 812 can be implemented by one or more integrated circuits, logic circuits, microprocessors or controllers from any desired family or manufacturer.

The processor 812 of the illustrated example includes a local memory 813 (e.g., a cache). The processor 812 of the illustrated example is in communication with a main memory including a volatile memory 814 and a non-volatile memory 816 via a bus 818. The volatile memory 814 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/or any other type of random access memory device. The non-volatile memory 816 may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory 814, 816 is controlled by a memory controller.

The processor platform 800 of the illustrated example also includes an interface circuit 820. The interface circuit 820 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface.

In the illustrated example, one or more input devices 822 are connected to the interface circuit 820. The input device(s) 822 permit(s) a user to enter data and commands into the processor 812. The input device(s) can be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a track-pad, a trackball, isopoint and/or a voice recognition system.

One or more output devices 824 are also connected to the interface circuit 820 of the illustrated example. The output devices 824 can be implemented, for example, by display devices (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display, a cathode ray tube display (CRT), a touchscreen, a tactile output device, a light emitting diode (LED), a printer and/or speakers). The interface circuit 820 of the illustrated example, thus, typically includes a graphics driver card, a graphics driver chip or a graphics driver processor.

The interface circuit 820 of the illustrated example also includes a communication device such as a transmitter, a receiver, a transceiver, a modem and/or network interface card to facilitate exchange of data with external machines (e.g., computing devices of any kind) via a network 826 (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, coaxial cable, a cellular telephone system, etc.).

The processor platform 800 of the illustrated example also includes one or more mass storage devices 828 for storing software and/or data. Examples of such mass storage devices 828 include floppy disk drives, hard drive disks, compact disk drives, Blu-ray disk drives, RAID systems, and digital versatile disk (DVD) drives.

The coded instructions 832 of FIG. 6 may be stored in the mass storage device 828, in the volatile memory 814, in the non-volatile memory 816, and/or on a removable tangible computer readable storage medium such as a CD or DVD.

FIG. 9 is a block diagram of an example processor platform 900 capable of executing the instructions of FIG. 7 to implement the example client device 160, the example media presenter 210, the example event listener 220, the example metadata handler 230, the example structure generator 232, the example file detector 234, the example duration setter 236, the example metadata retriever 238, the example metadata converter 240, the example transmitter 250 and/or the media monitor 165 of FIGS. 1 and/or 2. The processor platform 900 can be, for example, a server, a personal computer, a mobile device (e.g., a cell phone, a smart phone, a tablet such as an iPad™), a personal digital assistant (PDA), an Internet appliance, a DVD player, a CD player, a digital video recorder, a Blu-ray player, a gaming console, a personal video recorder, a set top box, or any other type of computing device.

The processor platform 900 of the illustrated example includes a processor 912. The processor 912 of the illustrated example is hardware. For example, the processor 912 can be implemented by one or more integrated circuits, logic circuits, microprocessors or controllers from any desired family or manufacturer. The example processor 912 implements the example media presenter 210, the example event listener 220, the example metadata handler 230, the example structure generator 232, the example file detector 234, the example duration setter 236, the example metadata retriever 238, the example metadata converter 240, the example transmitter 250 and/or the media monitor 165 of FIGS. 1 and/or 2.

The processor 912 of the illustrated example includes a local memory 913 (e.g., a cache). The processor 912 of the illustrated example is in communication with a main memory including a volatile memory 914 and a non-volatile memory 916 via a bus 918. The volatile memory 914 may be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/or any other type of random access memory device. The non-volatile memory 916 may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory 914, 916 is controlled by a memory controller.

The processor platform 900 of the illustrated example also includes an interface circuit 920. The interface circuit 920 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface.

In the illustrated example, one or more input devices 922 are connected to the interface circuit 920. The input device(s) 922 permit(s) a user to enter data and commands into the processor 912. The input device(s) can be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a track-pad, a trackball, isopoint and/or a voice recognition system.

One or more output devices 924 are also connected to the interface circuit 920 of the illustrated example. The output devices 924 can be implemented, for example, by display devices (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display, a cathode ray tube display (CRT), a touchscreen, a tactile output device, a light emitting diode (LED), a printer and/or speakers). The interface circuit 920 of the illustrated example, thus, typically includes a graphics driver card, a graphics driver chip or a graphics driver processor.

The interface circuit 920 of the illustrated example also includes a communication device such as a transmitter, a receiver, a transceiver, a modem and/or network interface card to facilitate exchange of data with external machines (e.g., computing devices of any kind) via a network 926 (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, coaxial cable, a cellular telephone system, etc.).

The processor platform 900 of the illustrated example also includes one or more mass storage devices 928 for storing software and/or data. Examples of such mass storage devices 928 include floppy disk drives, hard drive disks, compact disk drives, Blu-ray disk drives, RAID systems, and digital versatile disk (DVD) drives. The example mass storage 928 and/or the example memories 913, 914, 916 may store the table 260, the metadata tags 270, the playback positions 280, and/or the example multi-file counter 290.

The coded instructions 932 of FIG. 7 may be stored in the mass storage device 928, in the volatile memory 914, in the non-volatile memory 916, and/or on a removable tangible computer readable storage medium such as a CD or DVD.

As mentioned above, to accurately monitor a playback position of media on a client device, conventional media monitoring methods require monitors that are tailored for individual devices and/or families of devices. Examples disclosed herein provide advantages over such conventional monitoring methods by conserving data storage resources that would be required to store specialized monitors for the many different types of devices that are available to consumers. Examples disclosed herein also conserve network communication resources that would be required to provide such specialized monitors to individual devices for monitoring media at those devices.

Although certain example methods, apparatus and articles of manufacture have been disclosed herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture fairly falling within the scope of the claims of this patent. 

What is claimed is:
 1. An apparatus comprising: an event listener to listen for an event notification based on a playback position of a first media segment of a multi-segment media; a metadata handler to: update a multi-file counter with an offset based on a duration of the first media segment; detect that a second media segment is a segment of the multi-segment media; determine a playback time within the second media segment; add the playback time to the multi-file counter to determine a corresponding playback time of the multi-segment media; attempt to perform a lookup of a metadata tag in a table based on the playback time of the multi-segment media; and a transmitter to transmit the metadata tag corresponding to the playback time of the multi-segment media to an audience measurement entity.
 2. The apparatus of claim 1, wherein the table includes metadata tags and corresponding playback positions.
 3. The apparatus of claim 2, wherein the metadata handler is to generate the table based on information included in the first media segment of the multi-segment media.
 4. The apparatus of claim 3, wherein the table is based on information included in only the first media segment of the multi-segment media.
 5. The apparatus of claim 1, wherein the metadata handler is to, upon completion of playback of the second media segment, update the multi-file counter with the offset based on the duration of the second media segment.
 6. The apparatus of claim 5, wherein the metadata handler is to: detect that a third media segment presented intermediate the first media segment and the second media segment is not a segment of the multi-segment media; and upon completion of playback of the third media segment, omit updating of the multi-file counter.
 7. The apparatus of claim 6, wherein the third media segment is an advertisement.
 8. The apparatus of claim 1, wherein the metadata handler is to detect that the second media segment is a segment of the multi-segment media by detecting that a name of the second media segment is an incremented version of the name of the first media segment.
 9. The apparatus of claim 1, wherein the metadata handler is to detect that the second media segment is a segment of the multi-segment media by detecting that a name of the second media segment complies with a file naming convention for the multi-segment media.
 10. The apparatus of claim 1, wherein the transmitter is further to, in response to successful performance of the lookup, add the metadata tag to a list of metadata tags, and transmit the list of metadata tags.
 11. A non-transitory computer readable medium comprising instructions which, when executed, cause a machine to at least: listen for an event notification based on a playback position of a first media segment of a multi-segment media; update a multi-file counter with an offset based on a duration of the first media segment; detect that a second media segment is a segment of the multi-segment media; determine a playback time within the second media segment; add the playback time to the multi-file counter to determine a corresponding playback time of the multi-segment media; attempt to perform a lookup of a metadata tag in a table based on the playback time of the multi-segment media; and transmit the metadata tag corresponding to the playback time of the multi-segment media to an audience measurement entity.
 12. The non-transitory computer readable medium of claim 11, wherein the table includes metadata tags and corresponding playback positions.
 13. The non-transitory computer readable medium of claim 12, wherein the instructions when executed, further cause the machine to generate the table based on information included in the first media segment of the multi-segment media.
 14. The non-transitory computer readable medium of claim 13, wherein the table is based on information included in only the first media segment of the multi-segment media.
 15. The non-transitory computer readable medium of claim 11, wherein the instructions when executed, further cause the machine to, upon completion of playback of the second media segment, update the multi-file counter with the offset based on the duration of the second media segment.
 16. The non-transitory computer readable medium of claim 15, wherein the instructions when executed, further cause the machine to: detect that a third media segment presented intermediate the first media segment and the second media segment is not a segment of the multi-segment media; and upon completion of playback of the third media segment, omit updating of the multi-file counter.
 17. The non-transitory computer readable medium of claim 16, wherein the third media segment is an advertisement.
 18. The non-transitory computer readable medium of claim 11, wherein the instructions when executed, further cause the machine to detect that the second media segment is a segment of the multi-segment media by detecting that a name of the second media segment is an incremented version of the name of the first media segment.
 19. The non-transitory computer readable medium of claim 11, wherein the instructions when executed, further cause the machine to detect that the second media segment is a segment of the multi-segment media by detecting that a name of the second media segment complies with a file naming convention for the multi-segment media.
 20. The non-transitory computer readable medium of claim 11, wherein the instructions when executed, further cause the machine to, in response to successful performance of the lookup, add the metadata tag to a list of metadata tags, and transmit the list of metadata tags. 